chore(release): prepare v0.1.6#51
Merged
Merged
Conversation
Prepare the 0.1.6 release. Version bump (0.1.5 → 0.1.6) across all 9 version surfaces verified by publish.yml's tag-match checks: - root package.json + 7 package.json versions - codex/claude plugin.json versions - codex/claude/opencode .mcp.json / opencode.json @Version pins - 12 internal-dependency version pins (taskflow-core/-mcp/-hosts) - pnpm-lock.yaml regenerated (--frozen-lockfile passes) CHANGELOG: promote [Unreleased] → [0.1.6] — 2026-07-06, and add the two feats that shipped but were missing from the notes: defineFile (verify/ compile/run a flow from a path on disk) and JSONC comment support in flow definition files (parseJsonc). Docs consistency sweep (4 scout agents audited README/AGENTS/docs/skills/ per-package READMEs against ground truth): - Test count 1092 → 1140 (root README, all 6 per-package READMEs via copy-readme, RELEASE.md, CONTRIBUTING.md); zh-CN 1045 → 1140. - 'Unreleased (post-v0.1.5)' → 'v0.1.6 (current release)' in README status section (+ defineFile/JSONC added to the feature summary). - Stale 0.1.5 version refs in RELEASE.md, SECURITY.md, docs/codex-mcp.md, docs/claude-mcp.md → 0.1.6. - Fix broken #whats-inside anchor in README.zh-CN.md (heading is 内部构成; added an explicit <a id> anchor so the badge links resolve). Pre-flight green: typecheck 0 errors, 1140/1140 tests, build OK, skills no drift. Verified: no stale 1092/1123/1045/0.1.5/'Unreleased' remain.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release prep for v0.1.6. Merge this, then
git tag v0.1.6 && git push origin v0.1.6to triggerpublish.yml.What this does
1. Version bump 0.1.5 → 0.1.6 across every surface
publish.yml's tag-match checks verify:package.json+ 7packages/*/package.jsonversionplugin.jsonversions.mcp.json/opencode.json@versionpinstaskflow-core/-mcp/-hosts)pnpm-lock.yamlregenerated (--frozen-lockfilepasses)2. CHANGELOG — promote
[Unreleased]→[0.1.6] — 2026-07-06, and add the two feats that shipped but were missing from the notes:defineFileand JSONC comment support.3. Docs consistency sweep — 4 scout agents audited README / AGENTS / docs / skills / per-package READMEs against ground truth. Fixes:
1092(and zh-CN1045, README1123)1140Unreleased (post-v0.1.5)v0.1.6 (current release)+ added defineFile/JSONC to the feature summary0.1.5version refs0.1.6#whats-insideanchor<a id="whats-inside">anchorPre-flight (all green)
pnpm run typecheck— 0 errorspnpm test— 1140/1140 passpnpm run build— 7 packages emit dist1092/1123/1045/0.1.5/Unreleasedremain (grep-verified)Not blocking
npm_and_yarn in /. for postcssfailure onmainis a weekly security-scan workflow (event: dynamic), not a required check and not involved in tag-triggeredpublish.yml. Can be addressed separately by merging the dependabot PR.After merge
git tag v0.1.6 && git push origin v0.1.6publish.ymlverifies all 9 version surfaces match the tag, publishes the 7 packages to npm in dependency order (core → mcp → hosts → pi → codex → claude → opencode) with provenance, and cuts a GitHub Release from the[0.1.6]CHANGELOG section. Then verify: